Computing system deployment planning method

ABSTRACT

Management of the enterprise applications to maintain architectural integrity and performance of the entreprise applications is critical for providing avaliability of business services to users. When components of an application or computing system are moved between two systems, there is a need to reconfigure a previously configure system. Thus, the deployment requires complicated procedures that requires specialized training in the application being installed to ensure that system integrity is preserved at all times. A computing system deploymemt model introduces layers and clusters for segregating computing system, system and resources components based on their functionality and services provided thereby. Associations between components are registred in profiles to facilitate dependency tracking. The computer system deployment model allows for structured deployment of the computing system onto a host system. However, actual deployment of computing system components onto the host system is cost inefficient and time-consuming although components conflicts can be identified during the deployment stage. An embodiment of the invention facilitates deployment planning by utilising component profiles alone. A user mocks the actual deployment using a user interface to simulate different deployment configurations. The details of a successful mock deployment are captured for use in an actual deployment of the computing service and its components without compromise to the integrity of the host system. Cost consumption is also reduced by the alleviation of the need to use actual components during the deployment planning process.

FIELD OF INVENTION

The present invention relates generally to a computing systemdeployment. In particular, the invention relates to a computing systemdeployment planning method for planning the deployment of computingsystem components.

BACKGROUND

Conventional enterprise applications today possess multi-tierarchitectures. Unlike standalone applications in the past, theseenterprise applications provide specialized solutions catering todifferent business needs within an organization or across geographicallydistant installations. The elaborate structure of these enterpriseapplications gives rise to vast quantity of heterogeneous enterpriseback-end computing.

Management of the enterprise applications to maintain architecturalintegrity and performance of the enterprise applications is critical forproviding availability of business services to users, for examplecustomers.

The functions of the enterprise applications requiring managementincludes the deployment and configuration of service applications,system functionality diagnosis, maintenance of the integrity ofcomponent dependencies within an application and the monitoring andbalancing of application component loading for improving applicationperformance.

In the course of managing the enterprise applications, a situationrequiring components of an application to be moved between two systemsat different locations may arise. Alternatively, new resources may bemade available to the system the enterprise applications reside within.In both these situations, there is a need to reconfigure a previouslyconfigured system. In most cases, the deployment of an application orits components requires complicated procedures that requires specializedtraining in the application being installed as system integrity has tobe preserved at all times.

An enterprise application undergoes several configuration changes and afew versions of its associated components in the course of its life.Once an application is deployed within a system and becomes operational,it will undergo further component replacements, enhancements andexpansion in scale.

Keeping the dependencies and the integrity of large scale systemsbecomes problematic as different applications are provided by possiblydifferent vendors and the inter-connected systems, applications or itscomponents needs to be performed by a administrator who is deploying thesystems or applications. In such a situation, the dependencies andinter-connection requirements are provided to the administrator in theform of instructional manuals. Further knowledge of the requirements andlimitations of each system, application or its components is dependanton the experience and tacit capability of the administrator.

It is desirable to have a common method of capturing or specifying allthese information in a structured way, so that the dependencycalculations could be automated.

A computing system deployment method addresses the foregoing issues byintroducing layers and clusters for segregating computing system, systemand resource components based on their functionality and servicesprovided thereby. Associations between components are registered inprofiles to facilitate dependency tracking. The computing systemdeployment model allows for structured deployment of the computingsystem onto a first host system. The profiles further facilitatemigration of the computing system and its associated components onto asecond host system without compromising system integrity.

However, the use of actual components during the deployment may be costineffective although the compatibility of a component or the viabilityof a components configuration is identified during deployment.

Hence, this clearly affirms a need for a computing system deploymentplanning method for planning the deployment of a computing system andthe components thereof.

SUMMARY

In accordance with a first aspect of the invention, there is disclosed acomputing system deployment planning method comprising the steps of:

providing a plurality of components for modelling a computing system;

selecting a plurality of component icons, each component icon beingrepresentative of a component profile, each component profile beingassociated with a corresponding component;

invoking a dependency action between at least one pair of selectedcomponent icons, the dependency action being one of associating ordisassociating the at least one pair of selected component icons;

analysing dependency action requirements between the at least one pairof selected component icons in response to invoking the dependencyaction therebetween, the dependency action requirements being therequirements for associating or disassociating the at least one pair ofselected component icons;

providing a requirements compliance indication upon satisfying thedependency action requirements, the requirement compliance indicationfor indicating that the dependency action complies with the dependencyaction requirements; and

updating a deployment image with the at least one pair of selectedcomponent icons and the dependency actions therebetween in response tothe requirements compliance indication, the deployment image being arecord of the at least one pair of selected component icons andperformed dependency action.

In accordance with a second aspect of the invention, there is discloseda computing system deployment planning method comprising the steps of:

providing a plurality of components for modelling a computing system;

selecting a plurality of component icons being representative of acomponent profile, each component profile being associated with acorresponding component;

invoking a dependency action between at least one pair of selectedcomponent icons, the dependency action being one of associating ordisassociating the at least one pair of selected component icons; and

analysing the compatibility between the at least one pair of associatedcomponent icons in accordance to the corresponding component profiles,the component profile containing:

-   -   at least one association requirement;    -   at least one association restriction; and    -   at least one contract specification, each contract specification        indicating at least one parameter required by one component icon        from another component icon for association thereto.

In accordance with a third aspect of the invention, there is disclosed acomputing system deployment planning system comprising the means for:

providing a plurality of components for modelling a computing system;

selecting a plurality of component icons using a user interface, eachcomponent icon being representative of a component profile, eachcomponent profile being associated with a corresponding component, andthe plurality of component icons being selected by a user;

invoking a dependency action between at least one pair of selectedcomponent icons, the dependency action being one of associating ordisassociating the at least one pair of selected component icons;

analysing dependency action requirements between the at least one pairof selected component icons in response to invoking a dependency actiontherebetween, the dependency action requirements being the requirementsfor associating or disassociating the at least one pair of selectedcomponent icons;

providing a requirements compliance indication upon satisfying thedependency action requirements, the requirement compliance indicationfor indicating that the dependency action complies with the dependencyaction requirements; and

updating a deployment image with the selected component icons and thedependency actions therebetween in response to the requirementscompliance indication, the deployment image being a record of the atleast one pair of selected component icons and performed dependencyaction.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention are described hereinafter with reference tothe following drawings, in which:

FIG. 1 shows a block diagram representing a computing system deploymentmodel;

FIG. 2 shows a block diagram of a layer of the computing systemdeployment model of FIG. 1 with a plurality of components containedtherein being grouped in clusters;

FIG. 3 shows a block diagram of a component profile of each component ofFIG. 2;

FIG. 4 shows a block diagram of a deployment planning system inaccordance to an embodiment of the invention for planning the computingsystem deployment model of FIG. 1;

FIG. 5 shows a block diagram of the deployment planning system of FIG.4;

FIG. 6 shows a display representation of a graphical user interface(GUI) of the deployment planning system of FIG. 4; and

FIG. 7 shows a process flowchart of a computing system deploymentplanning method using the deployment planning system of FIG. 4.

DETAILED DESCRIPTION

A computing system deployment planning method for addressing theforegoing problems is described hereinafter.

An embodiment of the invention, a computing system deployment planningmethod is described with reference to FIGS. 1 to 7. The computing systemdeployment planning method is based on a computing system deploymentmodel 20. The computing system deployment model 20 is described withreference to FIG. 1, which shows a block diagram representing thecomputing system deployment model 20.

The computing system deployment planning method is for planning adeployment of a computing system (not shown) onto a computer-based hostsystem 22. The computing system comprises a plurality of components 24residing within the host system 22. These components 24 are generallyclassified as service components, system components and resourcecomponents (all not shown). These components 24 are organised into aplurality of layers 26 within the host system 22. The layers 26typically include a service layer, system layer and resource layer,which respectively contain service, system and resource components.

System components are conventionally known as server components and arefor providing computing system-based resources and services to othercomponents 24 within the host system 22. These system components are,for example, DNS servers, FTP servers, system libraries, Windowsregistries and key repositories. Resource components represent one of aphysical hardware that is associated with a computing node or a virtualdevice representing the physical hardware. Examples of hardwarerepresented by resource components include network cards, hard disks,and memory modules.

With reference to FIG. 2, the components 24 within each layer 26 aregrouped into clusters 28 based on the function thereof. FIG. 2 shows ablock diagram of one layer 26 of the computing system deployment model20. Each cluster 28 within each layer 26 contains at least one component24. In accordance to the computing system deployment model 20, theclusters 28 within the service layer, system layer and resource layerare referred to as the service clusters, system clusters and resourceclusters respectively.

The service clusters relate to services provided by the computingsystem, with each service cluster containing at least one servicecomponents relating to a particular service. The resource cluster andthe system cluster respectively contain resource components and systemcomponents having similar functions. The resource clusters include, forexample, a firewall cluster, a network router cluster, a network switchcluster, a computing server cluster and a storage cluster. The systemclusters include, for example, an operating system (OS) cluster, adatabase cluster and a virtual machine cluster.

In accordance with the computing system deployment model 20, a componentprofile 30 is associated with each component 24. A block diagram of thecomponent profile 30 is shown in FIG. 3. The component profile 30comprises a description 32 of the associated component 24, at least oneassociation requirement 34, at least one association restriction 36, andat least one contract specification 38, each contract specification 38indicating at least one parameter required by another component 24 forassociation therewith.

Additionally, the component profile 30 may further includes run-timeinformation (not shown) relating to how each component 24 is deployableand alterable parameters that affect the run-time behaviour of thecomponent 24. The run-time information includes installation paths,network ports and addresses, locations of application-specificconfiguration files and logs, and the like component configurationdetails. The run-time information is one of application-specific,domain-specific and vendor-specific and ensures substantial accuracy inplanning for the deployment of the computing system or the realisationof the computing system infrastructure.

Further in accordance with the computing system deployment model 20,each cluster 28 has an associated cluster profile 40 and each layer 26has an associated layer map 42. The cluster profile 40 provideinformation on the specification of the component 24, and the layer map42 of each layer 26 indicates the physical locality of the correspondingcomponent 24 within the host system 22, and the association of anothercomponent 24 therewith.

When deploying a computing system onto the host system 22, the componentprofiles 30 of the components 24 enables the assessment ofcompatibilities of associations therebetween and the identification ofassociation conflicts arising therefrom. However, the identification ofconflict and compatibility issues at the stage of deploying thecomponents 24 is both cost ineffective and time-consuming. The computingsystem deployment planning method alleviates the need to deploy theactual component 24 onto the host system 22 when planning for thedeployment of a computing system.

Components 24 for a related service are typically purchased from acomponent vendor. The computing system deployment planning method allowsfor the deployment of services or a computing system with just thecomponent profiles 30 of the required components 24. This allows acomponent vendor to supply component profiles 30 for deployment testingwithout the need to supply the components 24 until a purchase isrequired for the actual components 24.

The computing system deployment planning method is implemented using adeployment planning system 44. With reference to FIG. 4, which shows ablock diagram of the deployment planning system 44, the deploymentplanning system 44 resides on a computer-based system that is preferablynetworked for access to the Internet or a component profile server 46. Auser 48 interacts with the deployment planning system 44 through agraphical user interface (GUI) 50.

The deployment planning system 44 comprises a component profilerepository 52 containing a plurality of component profiles 30 as shownin FIG. 5. The component profiles 30 contained in the component profilerepository 52 are component profiles 30 for components 24 which areoften used. Additionally, component profiles 30 for other components aredownloadable from the Internet or the component profile server 46maintained by the component vendor.

Each component profile 30 contained within the component profilesrepository 52 is represented by a component icon 54. The component icons54 are presented to the user 48 through the GUI 50 on an icon palette 56thereof. FIG. 6 shows a display representation of the GUI 50, and FIG. 7shows a process flowchart of the computing system deployment methodusing the deployment planning system 44. Using the GUI 50 as shown inFIG. 6, the user 48 selects a plurality of component icons 54, in a step100 (of FIG. 7). The user 48 performs a drag-n-drop action to registerthe selection of the component icons 54 from the icon palette 56 onto aplanning palette 58 of the GUI 50.

Once the required component icons 54 are selected and registered on theplanning palette 58, the user 48 proceeds to perform dependency actionson the selected component icons 54, in a step 102 (of FIG. 7). Thedependency actions include associating at least one pair of componenticons 54 on the planning palette 58 by the user 48 performingdrag-n-drop actions.

Alternatively, a deployment image 60 is obtained from the componentprofile server 46. The deployment image 60 provides templates or samplesof previous computing system deployments. The deployment image 60 is arecord of selected component icons 54 and the associations (also knownas dependencies) therebetween. The deployment planning system 44includes a service constructor 62 as shown in FIG. 5. When thedeployment image 60 is required by the deployment planning system 44,the service constructor 62 reconstructs the selected component icons 54and the associations contained therein onto the planning palette 58. Thedependency actions further include disassociating at least one pair ofalready associated component icons 54, for example, from the deploymentimage 60 reconstruction by the service constructor 62.

The service constructor 62 emulates an environment of a previouslydeployed computing system by using the component icons 54 and thecorresponding component profiles 30. The component profiles 30 and theinformation contained therein alleviate the need to physically deploythe components 24.

The service constructor 62 constructs the deployment environment ontothe planning palette 58 of the GUI 50. The components 24 within a systemand associations therebetween are conventionally recorded in adeployment repository (not shown) in accordance to the computing systemdeployment model 20. The deployment repository is represented by adeployment image 60 within the deployment planning system 44 byrepresenting each component 24 with an associated component icon 54. Thedeployment image 60 coupled with the corresponding component 24 in thecomponent profiles repository 52 facilitates the emulation of aclose-to-reality deployment environment by the service constructor 62within the deployment planning system 44 and is visually presented tothe user 48 on the planning palette 58 of the GUI 50.

The deployment planning system 44 further includes a service analyser 64as shown in FIG. 5. For every dependency action performed, in a step 102(of FIG. 7), the service analyser 64 analyses dependency actionrequirements relating to the dependency action performed, in a step 104(of FIG. 7). The analysis of dependency action requirements is performedon-the-fly by the service analyser 64 in response to actions by the user48.

The run-time information of the component profile 30 is used forresource tracking by the service analyser 64. The run-time informationincludes installation paths, network ports and addresses, locations ofapplication-specific configuration files and logs, and the likecomponent configuration details. The service analyser 64 analyses thecomponent profile 30 and determines if the required run-time informationis available. If the required run-time information is unavailable, theuser 48 is prompted to provide the unavailable run-time information viathe GUI 50.

The run-time information is generally information based on a computingsystem's static configurations. As analysis by the service analyser 64is independent of actual run-time behaviours, it does not make therun-time information less accurate if the run-time information is keptup-to-date. Thus, the run-time information does generally provide areasonable representation of run-time behaviours.

The GUI 50 of the deployment planning system 44 includes a variation ofviews to enable the user 48 to better understand and track the selectedcomponent icons 54 on the planning palette 58 and the associationstherebetween. The variation of views preferably includes an intuitiveicon view with colour-coded line-connectors being visuallyrepresentative of the dependencies between one component icon 54 andanother associated component icon 54.

The variation of views preferably further includes a tree-viewdisplaying the selected component icons 54 within a tree structure. The“branches” of the tree structure allows the user 48 to determine theassociation or dependency of one component icon 54 to another componenticon 54. The variation of view preferably supports panning and zoomingfunctions (not shown). The panning function permits the user 48 tonavigate, using the GUI 50, and to select a specific component on theplanning palette 58 for further analysis. The zooming function allowsthe user 48 to either select an overall view of a deployed computingsystem or to “zoom-in” onto a particular component 24 for in-depthanalysis. Additional views, for example provided by a third-partyvendor, can be added to the GUI's 50 variation of views to provide theuser 48 with customised and/or improved visualisation tools.

When any two component icons 54 on the planning palette 58 of FIG. 6 areassociated, the component profiles 30 associated therewith are analysedby the service analyser 64. The association requirements 34 of eachcomponent icon 54 are analysed to discover the availability of otherrequired components icons 54 on the planning palette 58. The compliancebetween the two component icons 54 is also identified in accordance tothe association restrictions 36. Next, the availability of parametersfrom one component icon 54 for another component icon 54 is identifiedin accordance to the contract specifications 38 of both component icons54. The cluster profiles 40 of the clusters 28 containing the componenticons 54 allocated within are assessed for any conflicts therebetween.

If the associations are successful, a requirement compliance indicationis provided by the service analyser 64 and provided to the user 48through the GUI 50, in a step 106.

If any conflicts arise from the associations, the user 48 is providedwith an error message indicating the deficiency or problem arising fromthe intended associations between the component icons 54.

When any pair of component icons 54 on the planning palette 58 aredisassociated, the component profiles 30 associated therewith areanalysed by the service analyser 64. Any component icon 54 is unselectedby performing a drag-n-drop action to transfer the component icon 54from the planning palette 58 back onto the icon palette 56 using the GUI50. With each disassociation and unselecting of component icons 54, theassociation requirements 34- of each component icon 54 are analysed todiscover the dependency of other component icons 54 thereto. This is toprevent further conflicts from arising through the deployment actions ofdisassociation and unselecting. If the disassociations and unselectingof the component icons 54 are successful, a requirement complianceindication is provided to the user 48 through the GUI 50, in a step 106(of FIG. 7). If any conflicts arise from the associations, the user 48is provided with an error message indicating the problems arising fromthe intended disassociations between the component icons 54 and/or theunselecting of the component icons 54.

The deployment planning system 44 further includes a service imager 66as shown in FIG. 5. Once the user 48 completes planning for thedeployment of the required computing system or service, a new deploymentimage 60 is generated by the service imager 66 with the selectedcomponent icons 54 constructed on the planning palette 58 and theassociations therebetween, module 108 (of FIG. 7). Alternatively, theuser 48 has an option of updating an existing deployment image 60 usingthe service imager 66. The deployment image 60 is typically encryptedfor security. The encryption controls user access to the deploymentimage 60 by different users 48. A user's 48 ability to either use thecontents of the deployment image 60 and/or amend the contents therein isdetermined by different passwords used.

As shown in FIG. 5, the deployment planning system 44 further includes arealisation manager 68 and as shown in FIG. 3, the component profile 30further contains a resource utilisation indicator 62. The resourceutilisation indicator 62 enables the realisation manager 68 to perform asecondary action in response to the requirements compliance indication,in a step 106. The resource utilisation indicator 62 of each componenticon 54 provides information on the computing system resourcerequirements of the corresponding component 24 when deployed on the hostsystem 22. This enable the user to determine, with the deploymentplanning system 44, the current and future utilisation of computingsystem resources in accordance to the selected component icons 54reflected on the planning palette 58 and the associations therebetween

The realisation manager 68 assists the user 48 in realising a deploymentplan (not shown) created using the deployment planning system 44. Therealisation manager 68 generates a procurement list (not shown) for theuser 48 to execute the deployment plan systematically. The procurementlist allows the user to make the relevant purchase of components 24.Additionally, the realisation manager 68 generates a guideline todetermine the sequence and order of the components 24 for deployment.

In the foregoing manner, a computing system deployment planning methodis described according to an embodiment of the invention for addressingthe foregoing disadvantages of conventional practices for deployingcomputing systems. Although only one embodiment of the invention isdisclosed, it will be apparent to one skilled in the art in view of thisdisclosure that numerous changes and/or modification can be made withoutdeparting from the scope and spirit of the invention.

1. A computing system deployment planning method comprising the stepsof: providing a plurality of components for modelling a computingsystem; selecting a plurality of component icons, each component iconbeing representative of a component profile, each component profilebeing associated with a corresponding component; invoking a dependencyaction between at least one pair of selected component icons, thedependency action being one of associating or disassociating the atleast one pair of selected component icons; analysing dependency actionrequirements between the at least one pair of selected component iconsin response to invoking the dependency action therebetween, thedependency action requirements being the requirements for associating ordisassociating the at least one pair of selected component icons;providing a requirements compliance indication upon satisfying thedependency action requirements, the requirement compliance indicationfor indicating that the dependency action complies with the dependencyaction requirements; and updating a deployment image with the at leastone pair of selected component icons and the dependency actionstherebetween in response to the requirements compliance indication, thedeployment image being a record of the at least one pair of selectedcomponent icons and performed dependency action.
 2. The computing systemdeployment method as in claim 1, wherein each component profileconstitutes one of a plurality of component profiles provided within acomponent profiles repository, and each selected component icon beingrepresentative of one component profile available within the componentprofiles repository.
 3. The computing system deployment planning methodas in claim 1, wherein the step of obtaining a plurality of selectedcomponent icons comprises the steps of: registering selection of aplurality of component icons; and retrieving the component profilecorresponding to each selected component icon.
 4. The computing systemdeployment planning method as in claim 1, wherein the step of obtaininga plurality of selected component icons comprises the steps of:providing a deployment image, the deployment image being a record ofselected component icons and dependencies therebetween; retrieving thecomponent profile corresponding to each selected component icon; andestablishing dependencies between the selected component icons inaccordance to the deployment image.
 5. The computing system deploymentplanning method as in claim 1, wherein the component profile comprising:a description of the component; at least one association requirement; atleast one association restriction; and at least one contractspecification, each contract specification indicating at least oneparameter required from another component for association thereto. 6.The computing system deployment planning method as in claim 5, whereinthe step of obtaining a plurality of component icons comprises the stepsof: providing a plurality of layers on a host system, each layer havingan associated layer map, and the plurality of layers comprising: aservice layer; a system layer; and a resource layer; defining at leastone cluster in each of the plurality of layers, each cluster having anassociated cluster profile; and allocating each selected component iconinto one of the clusters defined in the plurality of layers.
 7. Thecomputing system deployment planning method as in claim 6, wherein thecluster profile of each cluster describes the general function of thecomponent represented by the component icon allocated therein, and thelayer map of each layer indicates the physical locality of thecorresponding component of each component icon within a host system, andthe association of another component icon with each component iconallocated therein.
 8. The computing system deployment planning method asin claim 7, wherein the step of invoking a dependency action comprisesthe step of: associating at least one pair of selected component icons.9. The computing system deployment planning method as in claim 8,wherein the step of analysing dependency action requirements comprisesthe steps of: analysing the component profiles of a source componenticon and a target component icon, the source and target component iconsconstituting any pair of associated component icons; discovering theavailability of other selected component icons required by theassociation requirements of the source component; identifying thecompliance of the target component in accordance to the associationrestrictions of the source component; and identifying the availabilityof parameters from the target component icon in accordance to thecontract specifications of the source component icons.
 10. The computingsystem deployment planning method as in claim 9, wherein the step ofanalysing dependency action requirements comprises the step of:analysing the cluster profiles of the clusters the source and targetcomponent icons are allocated thereto and identifying conflictstherebetween.
 11. The computing system deployment planning method as inclaim 7, wherein the step of invoking a dependency action comprises thestep of: disassociating at least one pair of selected component icons.12. The computing system deployment planning method as in claim 11,wherein the step of analysing dependency action requirements comprisesthe steps of: analysing the component profiles of a source componenticon and a target component icon, the source and target component iconsconstituting any pair of associated component icons in response to thestep of disassociation; and discovering the dependency of other selectedcomponent icons on the source component icon in accordance to theassociation requirements thereof.
 13. The computing system deploymentplanning method as in claim 12, wherein the step of disassociating thesource component icon and the target component icon comprises the stepof: unselecting the source component icon.
 14. The computing systemdeployment planning method as in claim 7, wherein the step of updatingthe deployment image comprises the steps of: updating the layer map ofeach layer; and registering the selected component icons and thedependencies therebetween onto the deployment image.
 15. The computingsystem deployment planning method as in claim 14, further comprising thestep of: initiating a secondary action in response to the step ofproviding a requirements compliance indication.
 16. The computing systemdeployment planning method as in claim 15, wherein the step ofinitiating a secondary action comprises the step of: quantifying currentutilisation of computing system resource in accordance to the selectedcomponent icons and the dependencies therebetween.
 17. The computingsystem deployment planning method as in claim 15, wherein the step ofinitiating a secondary action comprises the step of: quantifying futureutilisation of computing system resource in accordance to the selectedcomponent icons and the dependencies therebetween.
 18. A computingsystem deployment planning method comprising the steps of: providing aplurality of components for modelling a computing system; selecting aplurality of component icons being representative of a componentprofile, each component profile being associated with a correspondingcomponent; invoking a dependency action between at least one pair ofselected component icons, the dependency action being one of associatingor disassociating the at least one pair of selected component icons; andanalysing the compatibility between the at least one pair of associatedcomponent icons in accordance to the corresponding component profiles,the component profile containing: at least one association requirement;at least one association restriction; and at least one contractspecification, each contract specification indicating at least oneparameter required by one component icon from another component icon forassociation thereto.
 19. A computing system deployment planning systemcomprising the means for: providing a plurality of components formodelling a computing system; selecting a plurality of component iconsusing a user interface, each component icon being representative of acomponent profile, each component profile being associated with acorresponding component, and the plurality of component icons beingselected by a user; invoking a dependency action between at least onepair of selected component icons, the dependency action being one ofassociating or disassociating the at least one pair of selectedcomponent icons; analysing dependency action requirements between the atleast one pair of selected component icons in response to invoking adependency action therebetween, the dependency action requirements beingthe requirements for associating or disassociating the at least one pairof selected component icons; providing a requirements complianceindication upon satisfying the dependency action requirements, therequirement compliance indication for indicating that the dependencyaction complies with the dependency action requirements; and updating adeployment image with the selected component icons and the dependencyactions therebetween in response to the requirements complianceindication, the deployment image being a record of the at least one pairof selected component icons and performed dependency action.
 20. Thecomputing system deployment system as in claim 19, wherein eachcomponent profile constitutes one of a plurality of component profilesprovided within a component profiles repository, and each selectedcomponent icon being representative of one component profile availablewithin the component profiles repository.
 21. The computing systemdeployment planning system as in claim 19, wherein the means forobtaining a plurality of selected component icons comprises the meansfor: registering selection of a plurality of component icons; andretrieving the component profile corresponding to each selectedcomponent icon.
 22. The computing system deployment planning system asin claim 21, wherein the means for registering selection of a pluralityof component icons comprising: an icon palette containing a plurality ofcomponent icons; and a planning palette for receiving at least onecomponent icon selected by the user from the icon palette.
 23. Thecomputing system deployment planning system as in claim 19, wherein themeans for obtaining a plurality of selected component icons comprisesthe means for: providing a deployment image, the deployment image beinga record of selected component icons and dependencies therebetween;allocating at least one selected component icon from an icon paletteinto a planning palette in accordance to the deployment image, the iconpalette containing at least one component icon; retrieving the componentprofile corresponding to each selected component icon; and establishingdependencies between the selected component icons in accordance to thedeployment image.
 24. The computing system deployment planning system asin claim 19, wherein the component profile comprising: a description ofthe component; at least one association requirement; at least oneassociation restriction; and at least one contract specification, eachcontract specification indicating at least one parameter required fromanother component for association thereto.
 25. The computing systemdeployment planning system as in claim 24, wherein the means forobtaining a plurality of component icons comprises the means for:providing a plurality of layers on a host system, each layer having anassociated layer map, and the plurality of layers comprising: a servicelayer; a system layer; and a resource layer; defining at least onecluster in each of the plurality of layers, each cluster having anassociated cluster profile; and allocating each selected component iconinto one of the clusters defined in the plurality of layers.
 26. Thecomputing system deployment planning system as in claim 25, wherein thecluster profile of each cluster describes the general function of thecomponent represented by the component icon allocated therein, and thelayer map of each layer indicates the physical locality of thecorresponding component of each component icon within a host system, andthe association of another component icon with each component iconallocated therein.
 27. The computing system deployment planning systemas in claim 26, further comprising: an icon palette containing aplurality of component icons; and a planning palette for receiving atleast one component icon selected by the user from the icon palette. 28.The computing system deployment planning system as in claim 27, whereinthe means for invoking a dependency action comprises the means for:associating at least one pair of selected component icons receivedwithin the planning palette by the user using the user interface. 29.The computing system deployment planning system as in claim 28, whereinthe means for analysing dependency action requirements comprises themeans for: analysing the component profiles of a source component iconand a target component icon, the source and target component iconsconstituting any pair of associated component icons; discovering theavailability of other selected component icons required by theassociation requirements of the source component; identifying thecompliance of the target component in accordance to the associationrestrictions of the source component; and identifying the availabilityof parameters from the target component icon in accordance to thecontract specifications of the source component icons.
 30. The computingsystem deployment planning system as in claim 29, wherein the means foranalysing dependency action requirements comprises the means for:analysing the cluster profiles of the clusters the source and targetcomponent icons are allocated thereto and identifying conflictstherebetween.
 31. The computing system deployment planning system as inclaim 26, wherein the means for invoking a dependency action comprisesthe means for: disassociating at least one pair of selected componenticons received within the planning palette by the user using the userinterface.
 32. The computing system deployment planning system as inclaim 31, wherein the means for analysing dependency action requirementscomprises the means for: analysing the component profiles of a sourcecomponent icon and a target component icon, the source and targetcomponent icons constituting any pair of associated component icons inresponse to the means for disassociation; and discovering the dependencyof other selected component icons on the source component icon inaccordance to the association requirements thereof.
 33. The computingsystem deployment planning system as in claim 32, wherein the means fordisassociating the source component icon and the target component iconcomprises the means for: unselecting the source component icon receivedwithin a planning palette by the user using the user interface.
 34. Thecomputing system deployment planning system as in claim 26, wherein themeans for updating the deployment image comprises the means for:updating the layer map of each layer; and registering the selectedcomponent icons and the dependencies therebetween onto the deploymentimage.
 35. The computing system deployment planning system as in claim34, further comprising the means for: initiating a secondary action inresponse to the means for providing a requirements complianceindication.
 36. The computing system deployment planning system as inclaim 35, wherein the means for initiating a secondary action comprisesthe means for: quantifying current utilisation of computing systemresource in accordance to the selected component icons and thedependencies therebetween.
 37. The computing system deployment planningsystem as in claim 35, wherein the means for initiating a secondaryaction comprises the means for: quantifying future utilisation ofcomputing system resource in accordance to the selected component iconsand the dependencies therebetween.